Hi,

I finally got my lathe running on KMotionCNC tonight, however I'm struggling to get tool changes and canned cycles working via G code.

Tool changes work perfectly via the dropdown menu, or via the MDI, however putting the same code in a NC file, and it just gets skipped over.

I've tried M6T101 and T101M6, which both work via MDI, but do nothing in a file.

I had a look through the provided example G code files, however I couldn't see any that use an M6.

The other thing is trying to get a G83/Peck drilling cycle working.

Here's the code snippet I tried -

M6 T114 (6.8mm in Rear)
G0 X0 Z2
G83 X0 Z-32.0 R2 Q3 F100

G00 G53 X0 Z0

For the G83, the drill simply went straight to full depth, without any retracting/pecking.

Thanks,

Moray

Hi Moray,

I can't duplicate the problem, they both seem to work for me running the code you supplied. Console shows TooChange being called and the pecking action is going on.

What Version are you using?

Please try configuring for the simple

ToolChange.c

that just prints the tool to the console screen to determine if it is even being run.

Please post all your settings for M6, The Tool Offsets you are using, and your TP Settings.

Thanks
TK

On 4/6/2016 3:25 PM, Moray Cuthill moray.cuthill@... [DynoMotion] wrote:

Hi,

I finally got my lathe running on KMotionCNC tonight, however I'm struggling to get tool changes and canned cycles working via G code.

Tool changes work perfectly via the dropdown menu, or via the MDI, however putting the same code in a NC file, and it just gets skipped over.

I've tried M6T101 and T101M6, which both work via MDI, but do nothing in a file.

I had a look through the provided example G code files, however I couldn't see any that use an M6.

The other thing is trying to get a G83/Peck drilling cycle working.

Here's the code snippet I tried -

M6 T114 (6.8mm in Rear)
G0 X0 Z2
G83 X0 Z-32.0 R2 Q3 F100

G00 G53 X0 Z0

For the G83, the drill simply went straight to full depth, without any retracting/pecking.

Thanks,

Moray

Hi Tom,

I'm using the release version of 4.33.

I forgot to mention I did add a printf to the start of my M6 program, and nothing got printed to the console. It is like the M6 program is not being loaded.

My M6.c file simply copies the transferred value, into another persist variable, before invoking the main tool change function contained in my toolchange.c file. The reason for the separate file is I use the same function to recover the tool changer via a user button.

M6 setup is Exec/Wait/Sync to Thread 3, and Var 113.

These aren't the latest files from the lathe computer, however the only things I've (knowingly) changed since copying them to the lathe computer this afternoon, are the tool offsets have been updated, and a couple minor tweaks to axis channel settings.

Thanks,

Moray

On Wed, Apr 6, 2016 at 11:51 PM, Tom Kerekes tk@... [DynoMotion] <DynoMotion@yahoogroups.com> wrote:

Hi Moray,

I can't duplicate the problem, they both seem to work for me running the code you supplied. Console shows TooChange being called and the pecking action is going on.

What Version are you using?

Please try configuring for the simple

ToolChange.c

that just prints the tool to the console screen to determine if it is even being run.

Please post all your settings for M6, The Tool Offsets you are using, and your TP Settings.

Thanks
TK

On 4/6/2016 3:25 PM, Moray Cuthill moray.cuthill@... [DynoMotion] wrote:

Hi,

I finally got my lathe running on KMotionCNC tonight, however I'm struggling to get tool changes and canned cycles working via G code.

Tool changes work perfectly via the dropdown menu, or via the MDI, however putting the same code in a NC file, and it just gets skipped over.

I've tried M6T101 and T101M6, which both work via MDI, but do nothing in a file.

I had a look through the provided example G code files, however I couldn't see any that use an M6.

The other thing is trying to get a G83/Peck drilling cycle working.

Here's the code snippet I tried -

M6 T114 (6.8mm in Rear)
G0 X0 Z2
G83 X0 Z-32.0 R2 Q3 F100

G00 G53 X0 Z0

For the G83, the drill simply went straight to full depth, without any retracting/pecking.

Thanks,

Moray

Hi Moray,

I don't understand what your M6 C program does or how it invokes something else. Please post it if possible.

Var 113 is normally used for CSS Spindle control so there may be a Var conflict there, but I would still expect something printed unless your program doesn't print if it thinks the tool number is wrong.

Please try the ToolChange.c example.

Regards
TK

On 4/6/2016 4:09 PM, Moray Cuthill moray.cuthill@... [DynoMotion] wrote:

Hi Tom,

I'm using the release version of 4.33.

I forgot to mention I did add a printf to the start of my M6 program, and nothing got printed to the console. It is like the M6 program is not being loaded.

My M6.c file simply copies the transferred value, into another persist variable, before invoking the main tool change function contained in my toolchange.c file. The reason for the separate file is I use the same function to recover the tool changer via a user button.

M6 setup is Exec/Wait/Sync to Thread 3, and Var 113.

These aren't the latest files from the lathe computer, however the only things I've (knowingly) changed since copying them to the lathe computer this afternoon, are the tool offsets have been updated, and a couple minor tweaks to axis channel settings.

Thanks,

Moray

On Wed, Apr 6, 2016 at 11:51 PM, Tom Kerekes tk@... [DynoMotion] <DynoMotion@yahoogroups.com> wrote:

Hi Moray,

I can't duplicate the problem, they both seem to work for me running the code you supplied. Console shows TooChange being called and the pecking action is going on.

What Version are you using?

Please try configuring for the simple

ToolChange.c

that just prints the tool to the console screen to determine if it is even being run.

Please post all your settings for M6, The Tool Offsets you are using, and your TP Settings.

Thanks
TK

On 4/6/2016 3:25 PM, Moray Cuthill moray.cuthill@... [DynoMotion] wrote:

Hi,

I finally got my lathe running on KMotionCNC tonight, however I'm struggling to get tool changes and canned cycles working via G code.

Tool changes work perfectly via the dropdown menu, or via the MDI, however putting the same code in a NC file, and it just gets skipped over.

I've tried M6T101 and T101M6, which both work via MDI, but do nothing in a file.

I had a look through the provided example G code files, however I couldn't see any that use an M6.

The other thing is trying to get a G83/Peck drilling cycle working.

Here's the code snippet I tried -

M6 T114 (6.8mm in Rear)
G0 X0 Z2
G83 X0 Z-32.0 R2 Q3 F100

G00 G53 X0 Z0

For the G83, the drill simply went straight to full depth, without any retracting/pecking.

Thanks,

Moray

Hi Tom,

First thing is, I powered up the lathe tonight, and M6s are now working. I never changed anything from last night, just loaded it up, wrote a few lines of code to test a couple tool changes, and both M6Txxx and TxxxM6 worked.

I then ran a full file, and the M6 calls all worked.

The only tool issue I've got left, is how can I apply offsets automatically when as part of a tool change?

As it stands, although the tool is changed, the offsets don't get updated for the new tool.

Second thing is, I'm still getting issues with G83. Sometimes it works as it should, yet others it simply rapids to full depth. I ran through a full file cutting air, and the two G83s in it worked, yet when I loaded a bit bar, it simply done a single rapid move to full depth, paused briefly, then retracted to starting depth, before continuing on with the next line of code.

I then tried re-running the short bit test code I had, and first time through it done a rapid to final depth, but on the second run of code, it pecked as it should. Trying the full file again resulted in rapids to depth.

I've attached the actual tool table, and settings from the lathe, along with the file I was trying to run. All the M00's are so I can re-select the tool via the dropdown menu and get the correct offsets applied.

Moray

On Thu, Apr 7, 2016 at 12:22 AM, Tom Kerekes tk@... [DynoMotion] <DynoMotion@yahoogroups.com> wrote:

Hi Moray,

I don't understand what your M6 C program does or how it invokes something else. Please post it if possible.

Var 113 is normally used for CSS Spindle control so there may be a Var conflict there, but I would still expect something printed unless your program doesn't print if it thinks the tool number is wrong.

Please try the ToolChange.c example.

Regards
TK

On 4/6/2016 4:09 PM, Moray Cuthill moray.cuthill@... [DynoMotion] wrote:

Hi Tom,

I'm using the release version of 4.33.

I forgot to mention I did add a printf to the start of my M6 program, and nothing got printed to the console. It is like the M6 program is not being loaded.

My M6.c file simply copies the transferred value, into another persist variable, before invoking the main tool change function contained in my toolchange.c file. The reason for the separate file is I use the same function to recover the tool changer via a user button.

M6 setup is Exec/Wait/Sync to Thread 3, and Var 113.

These aren't the latest files from the lathe computer, however the only things I've (knowingly) changed since copying them to the lathe computer this afternoon, are the tool offsets have been updated, and a couple minor tweaks to axis channel settings.

Thanks,

Moray

On Wed, Apr 6, 2016 at 11:51 PM, Tom Kerekes tk@... [DynoMotion] <DynoMotion@yahoogroups.com> wrote:

Hi Moray,

I can't duplicate the problem, they both seem to work for me running the code you supplied. Console shows TooChange being called and the pecking action is going on.

What Version are you using?

Please try configuring for the simple

ToolChange.c

that just prints the tool to the console screen to determine if it is even being run.

Please post all your settings for M6, The Tool Offsets you are using, and your TP Settings.

Thanks
TK

On 4/6/2016 3:25 PM, Moray Cuthill moray.cuthill@... [DynoMotion] wrote:

Hi,

I finally got my lathe running on KMotionCNC tonight, however I'm struggling to get tool changes and canned cycles working via G code.

Tool changes work perfectly via the dropdown menu, or via the MDI, however putting the same code in a NC file, and it just gets skipped over.

I've tried M6T101 and T101M6, which both work via MDI, but do nothing in a file.

I had a look through the provided example G code files, however I couldn't see any that use an M6.

The other thing is trying to get a G83/Peck drilling cycle working.

Here's the code snippet I tried -

M6 T114 (6.8mm in Rear)
G0 X0 Z2
G83 X0 Z-32.0 R2 Q3 F100

G00 G53 X0 Z0

For the G83, the drill simply went straight to full depth, without any retracting/pecking.

Thanks,

Moray

Hi Moray,

I think normally within GCode Tool Length (and offset) compensation is turned on and off regardless of what tool is loaded with G43/G49. Can you add those to your GCode?

M6T101 (Right hand turning/facing)
G43H101

Regarding G83 are you able to come up with a sequence that plunges without pecking consistently?

Regards
TK

On 4/7/2016 12:40 PM, Moray Cuthill moray.cuthill@... [DynoMotion] wrote:

Hi Tom,

First thing is, I powered up the lathe tonight, and M6s are now working. I never changed anything from last night, just loaded it up, wrote a few lines of code to test a couple tool changes, and both M6Txxx and TxxxM6 worked.

I then ran a full file, and the M6 calls all worked.

The only tool issue I've got left, is how can I apply offsets automatically when as part of a tool change?

As it stands, although the tool is changed, the offsets don't get updated for the new tool.

Second thing is, I'm still getting issues with G83. Sometimes it works as it should, yet others it simply rapids to full depth. I ran through a full file cutting air, and the two G83s in it worked, yet when I loaded a bit bar, it simply done a single rapid move to full depth, paused briefly, then retracted to starting depth, before continuing on with the next line of code.

I then tried re-running the short bit test code I had, and first time through it done a rapid to final depth, but on the second run of code, it pecked as it should. Trying the full file again resulted in rapids to depth.

I've attached the actual tool table, and settings from the lathe, along with the file I was trying to run. All the M00's are so I can re-select the tool via the dropdown menu and get the correct offsets applied.

Moray

On Thu, Apr 7, 2016 at 12:22 AM, Tom Kerekes tk@... [DynoMotion] <DynoMotion@yahoogroups.com> wrote:

Hi Moray,

I don't understand what your M6 C program does or how it invokes something else. Please post it if possible.

Var 113 is normally used for CSS Spindle control so there may be a Var conflict there, but I would still expect something printed unless your program doesn't print if it thinks the tool number is wrong.

Please try the ToolChange.c example.

Regards
TK

On 4/6/2016 4:09 PM, Moray Cuthill moray.cuthill@... [DynoMotion] wrote:

Hi Tom,

I'm using the release version of 4.33.

I forgot to mention I did add a printf to the start of my M6 program, and nothing got printed to the console. It is like the M6 program is not being loaded.

My M6.c file simply copies the transferred value, into another persist variable, before invoking the main tool change function contained in my toolchange.c file. The reason for the separate file is I use the same function to recover the tool changer via a user button.

M6 setup is Exec/Wait/Sync to Thread 3, and Var 113.

These aren't the latest files from the lathe computer, however the only things I've (knowingly) changed since copying them to the lathe computer this afternoon, are the tool offsets have been updated, and a couple minor tweaks to axis channel settings.

Thanks,

Moray

On Wed, Apr 6, 2016 at 11:51 PM, Tom Kerekes tk@... [DynoMotion] <DynoMotion@yahoogroups.com> wrote:

Hi Moray,

I can't duplicate the problem, they both seem to work for me running the code you supplied. Console shows TooChange being called and the pecking action is going on.

What Version are you using?

Please try configuring for the simple

ToolChange.c

that just prints the tool to the console screen to determine if it is even being run.

Please post all your settings for M6, The Tool Offsets you are using, and your TP Settings.

Thanks
TK

On 4/6/2016 3:25 PM, Moray Cuthill moray.cuthill@... [DynoMotion] wrote:

Hi,

I finally got my lathe running on KMotionCNC tonight, however I'm struggling to get tool changes and canned cycles working via G code.

Tool changes work perfectly via the dropdown menu, or via the MDI, however putting the same code in a NC file, and it just gets skipped over.

I've tried M6T101 and T101M6, which both work via MDI, but do nothing in a file.

I had a look through the provided example G code files, however I couldn't see any that use an M6.

The other thing is trying to get a G83/Peck drilling cycle working.

Here's the code snippet I tried -

M6 T114 (6.8mm in Rear)
G0 X0 Z2
G83 X0 Z-32.0 R2 Q3 F100

G00 G53 X0 Z0

For the G83, the drill simply went straight to full depth, without any retracting/pecking.

Thanks,

Moray

Hi Tom,

I can add G43s easily enough.

I've just been and done some testing with G83s and have found the issue.

If you declare a G18 (Select X-Z plane), then the G83 rapids to depth, but not only that, it doesn't retract before the next move. I've attached a screen grab showing the moves. If you then run a code snippet such as the following (after the code shown in that screen grab)-

G90 G21
G00 G53 X0 Z0
(T101M6)
M6 T114
G43H114
G0 X0 Z2
(G1 Z1)
G83 X0 Y0 Z-32.0 R2 Q3 F100
G0 G53 X0 Z0
M30

the first time it runs, it also rapids to depth, then on subsequent re-runs, works as intended, until you then add a G18. However testing with only that snippet, the issue disappears as soon as the G18 is removed.

The G18s in my files all came from Mach3 files, as I've just been editing my old Mach3 files by changing the M6/tool change blocks to suit KMotionCNC. Now I know the problem, I'll just remove the G18s.

I'm guessing there's an issue with the G18 then having/needing Y declared in the G83. I won't go as far as saying it's a bug, as technically a G83 is a milling cycle, with the lathe equivalent being a G73, but it's something that should perhaps be highlighted somehow?

Thanks,

Moray

On Sat, Apr 9, 2016 at 7:04 PM, Tom Kerekes tk@... [DynoMotion] <DynoMotion@yahoogroups.com> wrote:

Hi Moray,

I think normally within GCode Tool Length (and offset) compensation is turned on and off regardless of what tool is loaded with G43/G49. Can you add those to your GCode?

M6T101 (Right hand turning/facing)
G43H101

Regarding G83 are you able to come up with a sequence that plunges without pecking consistently?

Regards
TK

On 4/7/2016 12:40 PM, Moray Cuthill moray.cuthill@... [DynoMotion] wrote:

Hi Tom,

First thing is, I powered up the lathe tonight, and M6s are now working. I never changed anything from last night, just loaded it up, wrote a few lines of code to test a couple tool changes, and both M6Txxx and TxxxM6 worked.

I then ran a full file, and the M6 calls all worked.

The only tool issue I've got left, is how can I apply offsets automatically when as part of a tool change?

As it stands, although the tool is changed, the offsets don't get updated for the new tool.

Second thing is, I'm still getting issues with G83. Sometimes it works as it should, yet others it simply rapids to full depth. I ran through a full file cutting air, and the two G83s in it worked, yet when I loaded a bit bar, it simply done a single rapid move to full depth, paused briefly, then retracted to starting depth, before continuing on with the next line of code.

I then tried re-running the short bit test code I had, and first time through it done a rapid to final depth, but on the second run of code, it pecked as it should. Trying the full file again resulted in rapids to depth.

I've attached the actual tool table, and settings from the lathe, along with the file I was trying to run. All the M00's are so I can re-select the tool via the dropdown menu and get the correct offsets applied.

Moray

On Thu, Apr 7, 2016 at 12:22 AM, Tom Kerekes tk@... [DynoMotion] <DynoMotion@yahoogroups.com> wrote:

Hi Moray,

I don't understand what your M6 C program does or how it invokes something else. Please post it if possible.

Var 113 is normally used for CSS Spindle control so there may be a Var conflict there, but I would still expect something printed unless your program doesn't print if it thinks the tool number is wrong.

Please try the ToolChange.c example.

Regards
TK

On 4/6/2016 4:09 PM, Moray Cuthill moray.cuthill@... [DynoMotion] wrote:

Hi Tom,

I'm using the release version of 4.33.

I forgot to mention I did add a printf to the start of my M6 program, and nothing got printed to the console. It is like the M6 program is not being loaded.

My M6.c file simply copies the transferred value, into another persist variable, before invoking the main tool change function contained in my toolchange.c file. The reason for the separate file is I use the same function to recover the tool changer via a user button.

M6 setup is Exec/Wait/Sync to Thread 3, and Var 113.

These aren't the latest files from the lathe computer, however the only things I've (knowingly) changed since copying them to the lathe computer this afternoon, are the tool offsets have been updated, and a couple minor tweaks to axis channel settings.

Thanks,

Moray

On Wed, Apr 6, 2016 at 11:51 PM, Tom Kerekes tk@... [DynoMotion] <DynoMotion@yahoogroups.com> wrote:

Hi Moray,

I can't duplicate the problem, they both seem to work for me running the code you supplied. Console shows TooChange being called and the pecking action is going on.

What Version are you using?

Please try configuring for the simple

ToolChange.c

that just prints the tool to the console screen to determine if it is even being run.

Please post all your settings for M6, The Tool Offsets you are using, and your TP Settings.

Thanks
TK

On 4/6/2016 3:25 PM, Moray Cuthill moray.cuthill@... [DynoMotion] wrote:

Hi,

I finally got my lathe running on KMotionCNC tonight, however I'm struggling to get tool changes and canned cycles working via G code.

Tool changes work perfectly via the dropdown menu, or via the MDI, however putting the same code in a NC file, and it just gets skipped over.

I've tried M6T101 and T101M6, which both work via MDI, but do nothing in a file.

I had a look through the provided example G code files, however I couldn't see any that use an M6.

The other thing is trying to get a G83/Peck drilling cycle working.

Here's the code snippet I tried -

M6 T114 (6.8mm in Rear)
G0 X0 Z2
G83 X0 Z-32.0 R2 Q3 F100

G00 G53 X0 Z0

For the G83, the drill simply went straight to full depth, without any retracting/pecking.

Thanks,

Moray

Group: DynoMotion	Message: 13098	From: Moray Cuthill	Date: 4/6/2016
Subject: KMotionCNC GCode canned cycles and tool changes

Group: DynoMotion	Message: 13099	From: Tom Kerekes	Date: 4/6/2016
Subject: Re: KMotionCNC GCode canned cycles and tool changes

Group: DynoMotion	Message: 13100	From: Moray Cuthill	Date: 4/6/2016
Subject: Re: KMotionCNC GCode canned cycles and tool changes

Group: DynoMotion	Message: 13101	From: Tom Kerekes	Date: 4/6/2016
Subject: Re: KMotionCNC GCode canned cycles and tool changes [3 Attachments]

Group: DynoMotion	Message: 13111	From: Moray Cuthill	Date: 4/7/2016
Subject: Re: KMotionCNC GCode canned cycles and tool changes

Group: DynoMotion	Message: 13122	From: Tom Kerekes	Date: 4/9/2016
Subject: Re: KMotionCNC GCode canned cycles and tool changes [3 Attachments]

Group: DynoMotion	Message: 13125	From: Moray Cuthill	Date: 4/9/2016
Subject: Re: KMotionCNC GCode canned cycles and tool changes